Skip to content

Current behavior for "What caused this updated?" when a lazy component resolves #22602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

eps1lon
Copy link
Collaborator

@eps1lon eps1lon commented Oct 20, 2021

Current behavior illustrating #22603

@eps1lon eps1lon marked this pull request as ready for review October 21, 2021 09:10
@eps1lon eps1lon force-pushed the feat/devtools/update-cause/unsuspend branch 2 times, most recently from cb4a9c7 to 47eea1f Compare March 8, 2022 10:04
@eps1lon eps1lon force-pushed the feat/devtools/update-cause/unsuspend branch from 47eea1f to 2ca2732 Compare July 2, 2022 08:11
Copy link

This pull request has been automatically marked as stale. If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated.

@github-actions github-actions bot added the Resolution: Stale Automatically closed due to inactivity label Apr 10, 2024
Copy link

Closing this pull request after a prolonged period of inactivity. If this issue is still present in the latest release, please ask for this pull request to be reopened. Thank you!

@github-actions github-actions bot closed this Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants